Question: why is this a 65k line PR

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ validbeck
❌ nrichers
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

@nibalizer related to this Slack DM, I changed the workflow that is causing issues to create PRs instead of committing directly to main. This version requires enabling auto-merge, would that be OK?

EDIT: afff438

Remove the defunct pdoc HTML output files, they are no longer being generated (and they would have been generated by a workflow anyway)
Remove the QMD files, as they get generated and committed as part of quarto-docs.yaml which runs on its own

Gotcha, I wasn't sure on either of these since the READMEs don't seem to have been updated to reflect these processes are covered — can we all maybe a callout or something to both the top-level README and the docs README?

@nrichers Sorry, it wouldn't let me checkout docs directory to main cleanly so I force-pushed to older commits. You'll need to reapply your edits.

Gotcha, I wasn't sure on either of these since the READMEs don't seem to have been updated to reflect these processes are covered — can we all maybe a callout or something to both the top-level README and the docs README?

We do have this in the docs/ readme:

.github/quarto-docs.yaml — Generates and commits Quarto Markdown docs

I guess we could be more explicit but since no user interaction is needed, there aren't really steps to follow?

I guess we could be more explicit but since no user interaction is needed, there aren't really steps to follow?

This is what is in the top-level README with no additional context:

This is what is in the top-level README with no additional context

Proving yet again that @validbeck not only writes excellent docs but also reads them. Removed in b6c7088

Proving yet again that @validbeck not only writes excellent docs but also reads them. Removed in b6c7088

Thank you — I wasn't sure if I was just lost! Maybe we can put a little note in the docs/README that when you test the generation locally you shouldn't commit the files because that's taken care of by the workflow.

EDIT: Actually, why are the builds committed to the .gitignore file? 🤔

PR Summary

This PR introduces two main categories of changes:

1. Workflow Enhancement for Documentation Generation:

   • The GitHub Actions workflow (.github/workflows/quarto-docs.yaml) has been updated to use the peter-evans/create-pull-request action instead of the previous add-and-commit action. This change automates the creation of a pull request for generated Quarto documentation updates rather than directly committing those changes.
   • Relevant parameters have been updated, such as setting a dedicated branch name (quarto-docs-update) and adding paths for the docs directory. The auto-merge step is provided as commented-out code, offering flexibility for future workflow enhancements.

2. API Endpoint Updates for Production:

   • Several R notebooks and R-related files have been modified to update the API host URLs from the development endpoint (https://api.dev.vm.validmind.ai/api/v1/tracking) to the production endpoint (https://app.prod.validmind.ai/api/v1/tracking).
   • This change affects files in the notebooks directory as well as documentation and initialization code in the validmind package, ensuring that examples and internal documentation point to the correct production environment.

Additionally, the .gitignore has been updated to ignore HTML and QMD files, likely to prevent auto-generated or intermediary files from being committed.

Test Suggestions

• Run the GitHub Actions workflow to verify that a pull request is properly created with updated documentation when changes occur.
• Manually verify that a new branch named 'quarto-docs-update' is created and cleaned up after the PR is merged.
• Test the generated Quarto documentation locally to ensure that the changes in file ignoring and automated updates are working as expected.
• Run the R notebook examples to confirm that the new production API endpoints are correctly used and that the functionality remains intact.